Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0429

reference
411-tree-1
name
0429
tree-preservation-order

undefined

411-tpo-1
uprn
address-text
point
POINT (-1.022382 50.890671)
geometry
MULTIPOLYGON (((-1.022296 50.890662,-1.022300 50.890679,-1.022312 50.890694,-1.022331 50.890706,-1.022354 50.890714,-1.022381 50.890717,-1.022407 50.890714,-1.022431 50.890707,-1.022450 50.890695,-1.022462 50.890680,-1.022467 50.890664,-1.022463 50.890647,-1.022451 50.890632,-1.022433 50.890620,-1.022409 50.890612,-1.022383 50.890609,-1.022356 50.890611,-1.022332 50.890619,-1.022313 50.890631,-1.022301 50.890646,-1.022296 50.890662)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL